Repository navigation
feat(web): add a run pipeline view for node status, timing, tokens and failures - #1198
Open
linus-liu-web wants to merge 1 commit into
Open
linus-liu-web wants to merge 1 commit into
linus-liu-web wants to merge 1 commit into
Conversation
…d failures On a run detail page the information about "what did this run actually do" is spread across tabs and interactions: node status lives on the graph, timing and tokens only show for the selected node, artifacts need a node click, failures show as a red status without the reason, and events are mixed into the live trace. On a seven-node SOP this is four places to check before you can answer "which step failed, how long did each take, how many tokens did it cost". Add a 流水 (pipeline) tab that aggregates the data already returned by GET /api/runs/:id: - a summary strip: run status, completed/failed node counts, wall time, total tokens, tool calls, retries/rework and artifact count + size; - one row per node in workflow order: status, duration, attempts/rework, tokens, tool calls, artifact count + size, plus the current activity or the failed node's real error; - expandable per-node detail: full error, current activity, artifacts (opening the existing artifact preview) and a truncated node output; - a run event timeline (last 40 events) rendered in one place. Frontend-only: no API, schema or engine change; it uses the node timing/usage/ error/activity fields, artifact metadata, event list and run usage that the run endpoint already returns.
2 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
On a run detail page, "what did this run actually do" is spread across tabs and interactions: node status lives on the graph, timing/tokens only show for the selected node, artifacts need a node click, a failed node shows a red status but the reason is buried, and events are mixed into the live trace. On a 7-node SOP you check four places before you can answer "which step failed, how long did each take, how many tokens did it cost".
Add a 流水 (pipeline) tab to the run detail view that aggregates data the API already returns:
Frontend-only: reuses
GET /api/runs/:id(nodeswith timing/usage/error/activity,artifactsmetadata,events,usage), so no API, schema or engine change is needed.#1191(capturing the real script/gate error into the node error) is still a separate backend fix; once it lands this view will show that error without further changes.Related: implements the proposal in #1197; complements #1101 / #1102 (run-detail truncation and artifact card layout) without changing those areas.
Scope
Compatibility
Frontend-only change: no API or data-store change, and no existing tab or action is modified. The new tab is read-only; runs without node state render an empty-state message.
observability.cssand theweb/index.htmlasset version are bumped so the new styles/scripts load, matching the repository's cache-busting convention.Validation
go vet ./webpasses.go test ./web -run TestRunPipelinePane -count=1passes: duration/byte formatting, workflow-order row ordering (including a run node missing from the workflow), summary math (nodes/tokens/tool calls/retries/artifacts), failed-node error rendering, running-node progress state, and timeline/expanded-detail markup.go test ./web -count=1(full package) passes.python3 scripts/check-public.pypasses.e2e/public) and a live platform deployment; this is a read-only view covered by the node test above.Safety